Conferences
For engineering leaders, “conference season” can feel like a relentless cycle of budget requests, travel approvals, and post-event report-backs. We send our teams, hoping they’ll soak up the latest tech, network with peers, and return brimming with inspiration. But too often, the impact feels… fleeting. A stack of business cards, a head full of buzzwords, and a quickly-forgotten slide deck.
As leaders, we need to shift our thinking. Conferences aren’t just professional development perks; they’re a strategic investment in knowledge management, and a critical component of building a learning organization. This isn't about sending people to conferences, it's about leveraging conferences for lasting team benefit.
By implementing a structured approach to conference attendance, engineering teams can maximize knowledge transfer, drive innovation, and achieve a greater return on investment. Here’s how to make the most of it.
The Problem with Passive Attendance
Think about the typical conference experience. Attendees rush from session to session, frantically taking notes, and trying to absorb everything. They network superficially, collecting contacts but not building meaningful relationships. Then they return to the office, get buried in their workload, and the valuable insights fade.
This isn’t a criticism of attendees. It's a symptom of a lack of pre-conference planning and post-conference follow-through. We, as leaders, are responsible for structuring the experience to maximize its impact.
A Four-Phase Approach to Conference Leverage
I've found a four-phase approach significantly improves the return on investment for conference attendance.
1. Pre-Conference: Strategic Alignment & Focused Learning
This is arguably the most important phase. Don't just ask people where they want to go. Guide them towards areas that align with specific team needs and priorities.
- Identify Knowledge Gaps: Before conference season kicks off, audit your team's skillsets and identify critical areas for growth. What new technologies are on the horizon? Where are we falling behind the competition? What are the biggest pain points we need to address?
- Align with Objectives: Tie conference attendance directly to team and company objectives. “Sarah, we’re exploring adopting Serverless architecture. I want you to attend KubeCon and focus specifically on sessions related to Knative and OpenFaaS. Your goal is to come back with a clear understanding of the pros and cons, and a recommendation for a potential proof-of-concept.” This provides focus and purpose.
- Pre-Conference Assignments: Have attendees research speakers and sessions beforehand. Ask them to identify 3-5 key takeaways they want to achieve. This forces proactive engagement.
- Budget & Logistics: While mundane, clear budgeting and travel policies prevent headaches. Consider tools like teamwork.com, which can facilitate task management and expense tracking during conference preparation.
| Knowledge Gap | Conference Topic | Attendee | Goals |
|---|---|---|---|
| Lack of Knative Expertise | KubeCon | Sarah | Understand pros/cons of Knative, identify POC opportunities |
| Limited Serverless Understanding | ServerlessConf | David | Explore different serverless frameworks, identify potential use cases |
2. During the Conference: Active Participation & Documentation
Encourage attendees to move beyond passive listening.
- Note-Taking System: Implement a standardized note-taking system. I recommend using a shared document (Google Docs, Confluence) so others can follow along in real-time. Encourage concise, actionable notes, not verbatim transcripts.
- “Teach-Back” Sessions: Encourage attendees to summarize key learnings with colleagues during the conference, even if it’s just a quick Slack message or a 5-minute call. For example, after a session on Reactive Programming, an attendee could quickly share the core concepts with a teammate and discuss how they might apply to a current project. Showtime (the meeting software) could be handy for these quick, informal check-ins with a small group.
- Networking with Intent: Don't just collect business cards. Encourage attendees to identify specific individuals or companies they want to connect with before the conference and schedule meetings in advance.
3. Post-Conference: Knowledge Sharing & Implementation
This is where many organizations fail. The knowledge gathered at the conference needs to be disseminated and applied.
- "Lunch & Learn" Sessions: Require attendees to present their key learnings to the team in a “Lunch & Learn” format. This is a low-pressure way to share information and spark discussion.
- Internal Wiki/Knowledge Base: Create a dedicated section in your internal wiki or knowledge base for conference learnings. This ensures the information is accessible to everyone, not just those who attended.
- Action Items & Follow-Up: Identify concrete action items based on conference learnings. "Based on Sarah's presentation, let's schedule a workshop to explore Knative further." Assign ownership and timelines.
- Experimentation & Prototyping: The ultimate goal is to apply new knowledge. Encourage experimentation with new technologies or approaches. Allocate time and resources for prototyping.
4. Measurement & Iteration: The Feedback Loop
Don't just send people to conferences and assume it's a good investment. Measure the impact.
- Post-Conference Survey: Ask attendees what they learned, how they plan to apply it, and what could have made the experience better.
- Track Action Item Completion: Monitor the progress of action items identified during the post-conference phase.
- Connect to Key Metrics: Look for ways to connect conference learnings to key metrics, such as code quality, development velocity, or customer satisfaction.
Implementing these steps requires commitment, but the long-term benefits outweigh the initial effort.
Conferences are a significant investment. By shifting our focus from simply attending to strategically leveraging these events, we can unlock a wealth of knowledge and drive meaningful innovation within our engineering teams. It's not about the swag; it’s about the sustainable impact.